Updating techniques for memory of a chassis management module

ABSTRACT

A technique for data roll-back includes in response to a first external static memory device being coupled to a first chassis management module and the first chassis management module being coupled to a middle plane board, determining whether the first external static memory device operates normally. In response to the first external static memory device operating normally, a controller of the first chassis management module writes data in the first external static memory device into a non-volatile memory of the first chassis management module to perform data roll-back.

This application is a continuation of U.S. patent application Ser. No.14/465,248 entitled “TECHNIQUES FOR UPDATING MEMORY OF A CHASSISMANAGEMENT MODULE,” filed Aug. 21, 2014, which claims priority toTaiwanese Patent Application 102130228, entitled “ELECTRONIC APPARATUSAND DATA ROLLING BACK METHOD THEREOF,” filed on Aug. 23, 2013. Thedisclosure of U.S. patent application Ser. No. 14/465,248 is herebyincorporated herein by reference in its entirety for all purposes.

BACKGROUND

The disclosure relates to updating memory and, more specifically, totechniques for updating memory of a chassis management module.

Each of a wide variety of conventional electronic apparatuses consistsof components arranged in an array. As one example, a blade serversystem comprises a plurality of blade servers arranged in an array. Theblade server system usually has a whole chassis and provides variousfunctions, such as power supply, computation, communication, and heatdissipation, in a centralized and united manner. As such, the bladesever system is a high-density system.

In general, the numerous blade servers (calculation nodes) are disposedin the front of a chassis to enhance convenience for a user and anadministrator. A chassis management module (CMM), a fan, and a powersupply have been disposed at the back of the chassis. In general, theblade servers, the fan, the power supply, and the chassis managementmodule are designed to be hot-swappable to enhance serviceability. Thedesign requires a middle board for supporting the hot swapping of theblade servers, the fan, the power, and the chassis management module.

The middle board is electrically connected to each of the componentsthrough a connector so as to transmit power signals, control high-speedsignals, and control low-speed signals. The middle board usually has anon-volatile memory, including but not limited to a flash read-onlymemory (ROM) or an electrically erasable programmable read-only memory(EEPROM). The non-volatile memory stores therein unerasable codes,including but not limited to vital product data (VPD) that includes, forexample, data pertaining to control, manufacturing, parts andcomponents. Typical VPD comprises a part number, a serial number, aproduct model number, a product version, a maintenance level, and theother specific information. Alternatively, VPD further comprisesuser-defined information. After a user has replaced the chassismanagement module, VPD data in the non-volatile memory of the middleboard is accessible through the system, such that maintenancetechnicians or R&D engineers can perform data analysis.

The non-volatile memory is an active component. The active component isdefined as an electronic component adapted to effectuate a gain in anelectrical circuit, so as to perform active functions such as amplifyingor oscillating when supplied with power. Persons skilled in the artunderstand that active components mounted on a circuit board aresusceptible to being damaged and becoming unreliable, thereby shorteningthe service life of the circuit board.

As its name indicates, the middle board is positioned centrally at theblade server system. It is difficult to perform maintenance operation onthe middle board in front or back of the chassis. As a result, tomaintain or replace the middle board it has been necessary to remove thechassis and then remove parts and components from the blade serversystem. Furthermore, when the middle board is damaged, it is difficultand inconvenient to read the data in the non-volatile memory of themiddle board. As such, the serviceability of the conventional middleboard is unsatisfactory in particular due to the non-volatile memory orother active components in use. The short service life of theconventional middle board causes many technical support problems.

BRIEF SUMMARY

A technique for data roll-back includes in response to a first externalstatic memory device being coupled to a first chassis management moduleand the first chassis management module being coupled to a middle planeboard, determining whether the first external static memory deviceoperates normally. In response to the first external static memorydevice operating normally, a controller of the first chassis managementmodule writes data in the first external static memory device into anon-volatile memory of the first chassis management module to performdata roll-back.

The above summary contains simplifications, generalizations andomissions of detail and is not intended as a comprehensive descriptionof the claimed subject matter but, rather, is intended to provide abrief overview of some of the functionality associated therewith. Othersystems, methods, functionality, features and advantages of the claimedsubject matter will be or will become apparent to one with skill in theart upon examination of the following figures and detailed writtendescription.

The above as well as additional objectives, features, and advantages ofthe present invention will become apparent in the following detailedwritten description.

BRIEF DESCRIPTION OF THE DRAWINGS

The description of the illustrative embodiments is to be read inconjunction with the accompanying drawings, in which:

FIG. 1 is a block diagram of an exemplary hardware framework of anelectronic apparatus configured according to an embodiment of thepresent disclosure;

FIG. 2 is a block diagram of a chassis management module configuredaccording to an embodiment of the present disclosure;

FIG. 3 is a schematic view of a chassis management module configuredaccording to an embodiment of the present disclosure;

FIG. 4 illustrates data backup and data roll-back between an externalstatic memory device and a non-volatile memory according to anembodiment of the present disclosure; and

FIG. 5 is a flowchart of a data roll-back process according to anembodiment of the present disclosure.

DETAILED DESCRIPTION

The illustrative embodiments provide techniques for updating memory of achassis management module.

In the following detailed description of exemplary embodiments of theinvention, specific exemplary embodiments in which the invention may bepracticed are described in sufficient detail to enable those skilled inthe art to practice the invention, and it is to be understood that otherembodiments may be utilized and that logical, architectural,programmatic, mechanical, electrical and other changes may be madewithout departing from the spirit or scope of the present invention. Thefollowing detailed description is, therefore, not to be taken in alimiting sense, and the scope of the present invention is defined by theappended claims and equivalents thereof.

It should be understood that the use of specific component, device,and/or parameter names are for example only and not meant to imply anylimitations on the invention. The invention may thus be implemented withdifferent nomenclature/terminology utilized to describe thecomponents/devices/parameters herein, without limitation. Each termutilized herein is to be given its broadest interpretation given thecontext in which that term is utilized. As may be used herein, the term‘coupled’ may encompass a direct connection between components orelements or an indirect connection between components or elementsutilizing one or more intervening components or elements.

The present disclosure discloses technology pertaining to an electronicapparatus that includes components arranged in an array withhigh-serviceability and high-reliability. The various embodimentsdisclose user-friendly solutions. In an embodiment, an electronicapparatus is disclosed that includes: a chassis; a middle plane boardwhich is disposed in the chassis and has a first side; a serverelectrically coupled to the middle plane board; a chassis managementmodule which is electrically coupled to the first side of the middleplane board in an extractable and insertable way and stores data relatedto components in the chassis; and an external static memory deviceelectrically coupled to the chassis management module in an extractableand insertable way.

An update of the data related to the components in the chassis is storedin the external static memory device in response to the electricalcoupling of the external static memory device to the chassis managementmodule and the electrical coupling of the chassis management module tothe middle plane board. A first middle plane board slot may be disposedon the first side and the chassis management module is electricallycoupled to the first middle plane board slot of the middle plane boardin a hot-swap way. The chassis management module may comprise a chassismanagement module slot and the external static memory device iselectrically coupled to the chassis management module slot in a hot-swapway.

The middle plane board may further have a second side opposite to thefirst side and the server is electrically coupled to the first side orthe second side of the middle plane board in an extractable andinsertable way. A second middle plane board slot may be disposed on thesecond side and the server is electrically coupled to the second middleplane board slot of the middle plane board in a hot-swap way. A thirdmiddle plane board slot may be disposed on the first side and the serveris electrically coupled to the third middle plane board slot of themiddle plane board in a hot-swap way. The chassis management module maycomprise a controller and a non-volatile memory and the update of thedata related to the components in the chassis may be stored in theexternal static memory device by the controller. The external staticmemory device may be extracted from the chassis management module andinserted into a second chassis management module.

Data in the external static memory device is written by the controllerinto a corresponding portion of the non-volatile memory to perform dataroll-back in response to the electrical coupling of the second chassismanagement module to the middle plane board. The server may comprise amanagement module and the chassis management module retrieves anoperation state of the server from the management module of the serverand monitors and manages the server according to the operation state.

In another embodiment, a data roll-back method applicable in anelectronic apparatus is disclosed. The electronic apparatus comprises achassis, a middle plane board, a server electrically coupled to themiddle plane board, a first chassis management module electricallycoupled to the middle plane board in an extractable and insertable way,and a first external static memory device electrically coupled to thefirst chassis management module in an extractable and insertable way.The first chassis management module comprises a controller and anon-volatile memory.

The method may comprise: inserting the first external static memorydevice into the first chassis management module for electrical couplingthereof; inserting the first chassis management module into the middleplane board for electrical coupling thereof; examining whether the firstexternal static memory device operates normally by means of the firstchassis management module; writing data which is in the first externalstatic memory device into a corresponding portion of the non-volatilememory by the controller to perform data roll-back in response to anormal operation of the first external static memory device.

The data roll-back method may further comprise: examining whether thefirst chassis management module operates normally; and removing thefirst external static memory device from the first chassis managementmodule, inserting the first external static memory device into a secondchassis management module operating normally, and rolling back data,which is in the first external static memory device, into the secondchassis management module by a controller of the second chassismanagement module in response to an abnormal operation of the firstchassis management module.

The data roll-back method may further comprise: sending from the firstchassis management module a message indicating an abnormal operation ofthe first external static memory device in response to the abnormaloperation of the first external static memory device. The data roll-backmethod may further comprise: extracting the first external static memorydevice from the first chassis management module and inserting a secondexternal static memory device capable of operating normally into thefirst chassis management module in response to the message indicatingthe abnormal operation of the first external static memory device.

An update of data related to components in the chassis is stored in thefirst external static memory device in response to the insertion of thefirst external static memory device into the first chassis managementmodule for electrical coupling thereof and the insertion of the firstchassis management module into the middle plane board for electricalcoupling thereof. A user examines whether the first chassis managementmodule operates normally by an indication of an indicator of the firstchassis management module.

Referring to FIG. 1, an exemplary hardware framework of an electronicapparatus 100, configured according to an embodiment of the presentdisclosure, is shown. The electronic apparatus 100 comprises a pluralityof servers 104, a power supply unit 108, a fan 112, a chassis managementmodule 116, an external static memory device 120, a middle plane board124, and a chassis 128. The electronic apparatus 100 is illustrativerather than restrictive of the present invention and the servers 104 canbe of different types.

In an embodiment, the electronic apparatus 100 may be, but is notlimited to, a blade server system. Each of the servers 104 may be, butare not limited to, blade servers and are electrically coupled to themiddle plane board 124. The quantity of the servers 104 is subject tochange as needed. The servers 104 perform data transmission andprocessing with the chassis management module 116, according to the typeof data and the way the data is processed. Each of the servers 104 iselectrically coupled to the middle plane board 124. In general, themiddle plane board 124 is a circuit board and connectors can be disposedon two sides thereof. Each of the components can be electrically coupledto the middle plane board 124 in a hot-swap way. In an embodiment, theblade servers 104 and the other components are electrically coupled tothe middle plane board 124 through high-pin-density connectors. The pinsmay transmit universal serial bus (USB) signals, high-speed signals,low-speed signals, and power signals. The servers 104 are disposed infront of the middle plane board 124 of the electronic apparatus 100.

To enhance their serviceability, the servers 104 can be hot-swappable.In an embodiment, each of the servers 104 comprises a management module132, including but not limited to, an integrated management module (IMM)or a baseboard management controller (BMC). The management modules 132manage the servers 104 through individual interfaces for performingfunctions, including but not limited to power management, system statedetection, event screening, power management, event occurrence logs, andsystem restore control. In an embodiment, each of the management modules132 comprises a microprocessor and a memory (not shown). For example,the baseboard management controller integrated with a motherboard (notshown) of each of the servers 104 can be referred to Maxim's VSC452baseboard management controller or ServerEngines' SE-SM4210-P01baseboard management controller and further modified or extended.

Depending on a sensor mounted on a corresponding one of the servers 104,each of the baseboard management controllers can obtain a temperatureparameter, a voltage parameter, a power consumption parameter, or anoperation state of the various combination of the parameters, so as tomonitor the information related to real-time operation of thecorresponding server 104 and a system condition. The chassis managementmodule 116 retrieves the operation state of each of the servers 104 fromthe baseboard management controller 132 of each of the servers 104through the middle plane board 124. Hence, the chassis management module116 can communicate with the baseboard management controllers 132 of theservers 104 and obtain the operation states from the baseboardmanagement controllers 132. After having obtained the operation statesof the servers 104, the chassis management module 116 further monitorsand manages the servers 104 according to the operation states.

Likewise, the aforesaid monitoring function performed by the chassismanagement module 116 also applies to the other components of theelectronic apparatus 100. For instance, the chassis management module116 monitors and manages the fan 112 according to the operation states.In an embodiment, through a port (not shown), the chassis managementmodule 116 communicates with a baseboard management controller (notshown) of the fan 112 and controls its rotational speed. The baseboardmanagement controller retrieves the real-time operating rotational speedof the fan 112 and forwards it to the chassis management module 116.After having obtained the operation states, such as the internaltemperature or the temperature at the other parts, of the servers 104,the chassis management module 116 regulates the rotational speed of thefan 112 in real-time.

In another embodiment, one of the management modules 132 is anintegrated management module, for example. The constituent elements ofthe integrated management module are similar to those of the baseboardmanagement controller and include an integrated management modulefirmware (IMM firmware) (not shown) of a server 104, which substitutesfor the baseboard management controller to integrate server processorfunctionality, super I/O, video controller, and remote functionalityinto a chip (not shown) mounted on the motherboard of the server 104.Moreover, the integrated management module firmware may include thecommands and routines that execute disclosed functionalities. In anembodiment, the management module 132 may be an iMM controller for usein IBM™ products. In another embodiment, depending on related needs, themanagement module 132 further comprises a remote control program (notshown) and an Intelligent Platform Management Interface (IPMI, notshown) utility.

In another embodiment, the blade server system 100 further comprises anoptical fiber module (not shown) for transmitting data processed by theservers 104, a switch server (not shown) for transmitting RJ45 networksignals, and a display unit (not shown) for displaying the condition ofcomponents in the blade server system 100. Each of the aforesaidcomponents is attributed to the prior art and well known among personsskilled in the art, and thus is not described further herein for thesake of brevity. Related operations and details of the components of theelectronic apparatus 100 are explained later. The power 108, the fan112, the chassis management module 116, or related ones of the servers104 can be disposed behind the middle plane board 124 of the electronicapparatus 100.

To enhance serviceability, the components (including the power 108, thefan 112, the chassis management module 116, or related ones of servers104) are coupled to the middle plane board 124 and are hot-swappable.The external static memory device 120 includes, but is not limited to, aUSB key in which a plurality of data is stored. The USB key 120 iselectrically coupled to the chassis management module 116 in anextractable and insertable way and engaged in communication, which takesplace through an external port of the chassis management module 116.

With brief reference to FIG. 2, data stored in a non-volatile memory 208of the chassis management module 116 and/or updates of the data arebacked up in the external static memory device 120. Data stored in theexternal static memory device 120 can also be rolled back to thenon-volatile memory 208 of the chassis management module 116. Therelated operations and details of the aforesaid data backup and dataroll-back are described below. In addition to the USB key, the externalstatic memory device 120 may further comprise a memory device supportingthe interface of the chassis management module 116, such as a securedigital memory card (SD memory card), or a device for supporting serviceprovider interface (SPI) or any other memory device.

Referring to FIG. 2, a block diagram of the chassis management module116 is illustrated. The chassis management module 116, also known as achassis supporting device, configures and manages parts and componentsmounted in the chassis 128. The chassis management module 116 comprisesa controller 204 and the non-volatile memory 208. The non-volatilememory 208 includes, but is not limited to, a flash ROM or anelectrically erasable programmable read only memory (EEPROM).Furthermore, the non-volatile memory 208 is defined with a protectedarea 212 and a flash area 216. Stored in the protected area 212 isunerasable code including, but not limited to, VPD such as invariableinformation related to parts, component, and manufacturing. The flasharea 216 stores user setting, event logs received via the controller204, chassis configuration, system control setting, and fan/power supplyunit fail information (fan/PSU fail information). The related operationsand details of the components of the chassis management module 116 aredescribed below.

FIG. 3 is a schematic view of the chassis management module 116according to another embodiment. As mentioned, the chassis managementmodule 116 processes a large amount of data in order to configure andmanage the components in the chassis 128. The chassis management module116 has a panel 300. Mounted on the panel 300 are various indicators andports including, but not limited to, a power light-emitting diode (LED)304, a heartbeat LED 308, a locator LED 312, a CHK LED 316, an Ethernetport activity LED 320, an Ethernet port link LED 324, and an MINI USB328. The LEDs indicate various predefined states that are well knownamong persons skilled in the art and are not described further hereinfor the sake of brevity.

The chassis management module 116 further comprises at least one slot220, including, but not limited to, a USB slot. The external staticmemory device 120 is connected to the chassis management module 116 in ahot-swap way. For example, the external static memory device 120 mayinclude a USB plug (not shown) connectable to the USB slot 220 of thechassis management module 116. The external static memory device 120 iselectrically coupled to the chassis management module 116 in a hot-swapway and removable from the chassis management module 116.

FIG. 4 illustrates a technique of data backup and data roll-back betweenthe external static memory device 120 and the non-volatile memory 208(including the protected area 212 and the flash area 216). In oneembodiment, the non-volatile memory 208 is a 32 KB EEPROM and is definedwith a plurality of data areas. An area 404 stores data (such as a partnumber) related to a field replaceable unit (FRU) of the chassismanagement module (CMM), for example. An area 408 stores data (such as apart number) related to a field replaceable unit (FRU) of the system(SYS), for example. The area 404 and the area 408 belong to theprotected area 212. An area 412 stores power budget-related data, forexample. An area 416 stores event logs in a system event log (SEL) file,for example. An area 420 is a reserve area, for example. An area 424 isa redundancy reserve area, for example. The area 412, area 416, area420, and area 424 belong to the flash area 216. The area 420 and area424 store various user setting and various event logs as needed.

In an embodiment, an interface 456 (between the external static memorydevice 120 and the controller 204) is a USB 1.1 and an interface 460(between the controller 204 and the non-volatile memory 208) is aninter-integrated circuit (I2C) bus. The external static memory device120 stores therein a plurality of data (data 1, data 2, data 3 . . .data n). In the event of a change in the data stored in the non-volatilememory (EEPROM) 208, such as a change in user setting or creation ofevent logs, the changed or updated data can be backed up in theplurality of data in the external static memory device 120 through theoperation of the controller 204. There are various methods of backing upthe data in the non-volatile memory 208 to the external static memorydevice 120. For example, backup may include: immediate backup in whichbackup occurs at the fastest speed possible as soon as a change happens;routine backup which occurs regularly and is configured by a userthrough a predetermined webpage to decide on the type and quantity ofbackup data; and conventional manual backup.

In an embodiment, because the routine backup is executed regularly, theroutine backup returns to the top of log space to continue with backupwhenever all available log space runs out. The backup techniques areattributed to the prior art related to this field and are not furtherdescribed in detail herein for the sake of brevity. After the externalstatic memory device 120 has been inserted into the chassis managementmodule 116 and the chassis management module 116 has been inserted intothe middle plane board 124, data roll-back may occur to the non-volatilememory 208 according to the data stored in the external static memorydevice 120. In an embodiment, a plurality of data in the external staticmemory device 120 is written to corresponding portions of thenon-volatile memory 208 through the operation of the controller 204 soas to effectuate data roll-back. If the data backup is not finished andthe data stored in the external static memory device 120 is incomplete,the controller 204 may execute data roll-back based on a previousversion of data stored in the external static memory device 120 andstore the event log in the system event log (SEL).

Upon delivery of the electronic apparatus 100, the external staticmemory device 120 stores delivery data in the protected area 212 only.In an embodiment, the area 404 stores related delivery data of a fieldreplaceable unit of the chassis management module, whereas the area 408stores related delivery data of a field replaceable unit of the system.The area 404 and area 408 belong to the protected area 212. The area412, the area 416, the area 420, and the area 424 shown in FIG. 4 do notstore any data. After the electronic apparatus 100 has operated for awhile, various user setting and various event logs are recorded in theflash area 216 based on actual conditions. Given the data backup methods(i.e. immediate backup, routine backup, manual backup, etc.), updateddata of various user setting and various event logs is backed up in theexternal static memory device 120.

Afterward, if the chassis management module 116 has to be replaced forany reason (for example, the chassis management module 116 has beendamaged), the user will only need to remove the external static memorydevice 120 from the damaged chassis management module 116 and insert theexternal static memory device 120 into another new chassis managementmodule 116. Meanwhile, the controller 204 of the new chassis managementmodule 116 rolls back the data in the external static memory device 120to the new chassis management module 116 automatically. A data roll-backmethod applicable in the electronic apparatus 100 according to anembodiment is illustrated with FIG. 1 through FIG. 4 which show relatedstructures and FIG. 5 which shows a flowchart.

Referring to FIG. 5, a data roll-back method 500 with respect to theelectronic apparatus 100, according to an embodiment, is illustrated.The data roll-back method 500 comprises various blocks. In block 504 theexternal static memory device 120 is coupled to the chassis managementmodule 116 (for example, in a hot-swap way) and the chassis managementmodule 116 is coupled to the middle plane board 124 (for example, in ahot-swap way). At this point in time, the chassis management module 116obtains data in the external static memory device 120 and thereby knowsthe system environment and user settings.

In another embodiment, the chassis management module 116 first reads asegment code in the protected area 212. Smooth reading is indicative ofcompliance with security mechanism. Then, the chassis management module116 further obtains all the data in the external static memory device120. In block 508, the chassis management module 116 examines whetherthe external static memory device 120 operates normally. The examinationincludes, but is not limited to, examining whether the initial state ofthe external static memory device 120 is a healthy state or whether theexternal static memory device 120 is present. Upon determination thatthe external static memory device 120 does not operate normally, theprocess flow of the method goes to block 512. Upon determination thatthe external static memory device 120 operates normally, the processflow of the method goes to block 520.

In block 512, the chassis management module 116 sends a messageindicating an abnormal operation of the external static memory device120 to a user. In an embodiment, if the chassis management module 116 isunable to write/read to/from the external static memory device 120 or ifthe chassis management module 116 is unable to detect the presence ofthe external static memory device 120, the CHK LED 316 (yellow in color,for example,) on the panel of the chassis management module 116 isturned on to display a message that the external static memory device120 fails or is incapable of normal operation. The event log of failureor abnormal operation is also written to the flash area 216 of thenon-volatile memory 208.

In block 516, the external static memory device 120 that fails may bereplaced by the user. Block 516 is followed by block 504, such thatblock 504 and subsequent blocks are carried out again. In block 520,data in the external static memory device 120 is automatically rolledback to the non-volatile memory 208 of the chassis management module 116in response to normal operation of the external static memory device120. In block 524, normal operation of the system is performed by theelectronic apparatus 100. In block 528, the user examines whether thechassis management module 116 operates normally. If the chassismanagement module 116 does not operate normally, the process flow of themethod goes from block 528 to block 532. If the chassis managementmodule 116 operates normally, the process flow of the method goes fromblock 528 to block 524.

In an embodiment, if the heartbeat LED 308 (for example, green in color)stops flashing, it indicates that the chassis management module 116 isnot operating normally. In another embodiment, the chassis managementmodule 116 has a network jack (not shown) and if a remote link does notgive any response, it indicates that the chassis management module 116does not operate normally (for example, the chassis management module116 fails or is erroneously set). In block 532, the user removes thechassis management module 116 from the middle plane board 124 when thechassis management module 116 does not operate normally. In block 536,the external static memory device 120 is removed from the chassismanagement module 116 and the external static memory device 120 isinserted into another new chassis management module 116 by the user. Thecontroller 204 of the new chassis management module 116 automaticallyrolls back data in the external static memory device 120 to the newchassis management module 116.

Then, the process flow of the method goes to block 504, such that block504 and subsequent blocks are carried out again. In a subsequent block,for example, a typical system operation starts a standby state. Theother basic frameworks and components of the electronic apparatus 100can be referred to conventional personal computers or servers, such asthe IBM Blade Center or the like. Hence, details attributed to theelectronic apparatus 100 but not related to the present disclosure areomitted from the description.

According to an embodiment, the middle plane board 124 does not have anyactive component and, thus, is a circuit board having only passivecomponents with high reliability and a long service life. The longservice life of the middle plane board 124 reduces the likelihood of theneed to replace the middle plane board 124 and to seek support frommaintenance technicians. Furthermore, according to the data backup anddata roll-back technique disclosed herein, a user can choose differentdata backup methods for backing up data, such as VPD, various usersettings, and various event logs, in the external static memory device120 as needed. A user can determine that data stored in the externalstatic memory device 120 is real-time and up-to-date. Hence, theexternal static memory device 120 may be inserted into any other chassismanagement module 116 and real-time and up-to-date data is then rolledback to the non-volatile memory 208 of the other chassis managementmodules 116. Furthermore, the external static memory device 120 isadvantageously portable and data stored in the external static memorydevice 120 can be read by appropriate software installed on anycomputer. Data at a chassis-level may also be easily backed up andtransferred. When it is necessary to replace the chassis managementmodule, data in the old chassis management module can be convenientlyrestored/rolled back to the new chassis management module, therebydispensing with the hassle of performing any additional settings.

According, techniques have been disclosed herein that advantageouslyupdate memory of a chassis management module in an efficient manner.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

While the invention has been described with reference to exemplaryembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the invention. Inaddition, many modifications may be made to adapt a particular system,device or component thereof to the teachings of the invention withoutdeparting from the essential scope thereof. Therefore, it is intendedthat the invention not be limited to the particular embodimentsdisclosed for carrying out this invention, but that the invention willinclude all embodiments falling within the scope of the appended claims.Moreover, the use of the terms first, second, etc. do not denote anyorder or importance, but rather the terms first, second, etc. are usedto distinguish one element from another.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the invention. Asused herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below, if any, areintended to include any structure, material, or act for performing thefunction in combination with other claimed elements as specificallyclaimed. The description of the present invention has been presented forpurposes of illustration and description, but is not intended to beexhaustive or limited to the invention in the form disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The embodiments were chosen and described in order to best explain theprinciples of the invention and the practical application, and to enableothers of ordinary skill in the art to understand the invention forvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method of data roll-back, comprising: inresponse to a first external static memory device being coupled to afirst chassis management module and the first chassis management modulebeing coupled to a middle plane board, determining, by the first chassismanagement module, whether the first external static memory deviceoperates normally; and in response to the first external static memorydevice operating normally, writing, by a controller of the first chassismanagement module, data in the first external static memory device intoa non-volatile memory of the first chassis management module to performdata roll-back.
 2. The method of claim 1, further comprising: inresponse to the first external static memory device being removed fromthe first chassis management module and coupled to a second chassismanagement module that is coupled to the middle plane board, storing,using a controller of the second chassis management module, roll-backdata that is stored in the first external static memory device to anon-volatile memory of the second chassis management module.
 3. Themethod of claim 1, wherein whether the first chassis management moduleoperates normally is indicated by an indicator of the first chassismanagement module.
 4. The method of claim 1, further comprising:sending, from the first chassis management module, a message indicatingan abnormal operation of the first external static memory device inresponse to the abnormal operation of the first external static memorydevice.
 5. The method of claim 1, wherein an update of data related tocomponents in a chassis is stored in a second external static memorydevice in response to removal of the first external static memory devicefrom the first chassis management module and the insertion of the secondexternal static memory device into the first chassis management module.6. The method of claim 1, wherein an update of data related tocomponents in the chassis is stored in the first external static memorydevice in response to the insertion of the first external static memorydevice into the first chassis management module.